Notes/Domino Fix List
 |  |
| SPR # PJAN4F5T93 | Fixed in 5.0.1c; 5.0.2c; 5.0.3 release |  |
Product Area: Other Technical Area: API Platform: Cross Platform
SPR #PJAN4F5T93 - Fix a problem with NSFNoteComputeWithForm which caused a memory overwrite when a date was stored in a text field and the date was in the year 2000 or greater. One of the manifestations of the problem was a crash in Agent Manager when agents created mail messages using the R4.6x mail stationery, "Gray Gradient with Lines," when the form was stored in the document. There could be other manifestations depending on the memory configuration on any given system. This problem affects both clients and servers.
Technote Number: 1088450
Problem:
Lotus has identified a potential fix that appears to address all reported
occurrences of this issue. We are working with all due diligence to make
corrected code available via Quarterly Maintenance Updates (QMUs) as soon as
possible. Current plans are to release R4.5.6c, R4.5.7g, R4.6.3d, R4.6.4d,
R4.6.5c, R4.6.6c, R5.0b, R5.0.1c, and R5.0.2c with the fix and to include it in
all upcoming Quarterly Maintenance Releases (QMRs) [that is, R4.6.7, R5.0.3,
and forward].
The following QMUs/QMR's are now available for download from Notes.Net:
Domino and Notes 4.6.6c
Domino and Notes 4.5.7g
Domino and Notes 5.0.2c
Domino and Notes 4.6.7
Domino and Notes 5.0.3
Excerpt from the Lotus Domino and Lotus Notes QMU and QMR fix lists:
API
- SPR# PJAN4F5T93 - Fix a problem with NSFNoteComputeWithForm which caused a
memory overwrite when a date was stored in a text field and the date was in the
year 2000 or greater. One of the manifestations of the problem was a crash in
Agent Manager when agents created mail messages using the R4.6x mail
stationery, "Gray Gradient with Lines," when the form was stored in the
document. There could be other manifestations depending on the memory
configuration on any given system. This problem affects both clients and
servers.
In most cases, the issue has been seen when you send a mail message that
includes a copy of a document and that document tries to force a post-1999 (or
pre-1950) date value into a text field. For example, the problem has been
identified in some cases in which a mail message attempts to manipulate a copy
of a document that has a time/date value stored but defined on the form as a
Text field. The issue occurs in cases where the included document's Form
contains a Text field that is being populated by a date value, for example:
@Created. As the document is being copied into the new message, a conversion
takes place that results in a crash. This issue can occur if the date value in
the Text field is prior to 1950 or any year after 1999, not just for the year
2000. The issue does not occur in all Forms that have a Text field set to a
date.
To avoid the crash, use one of the following workarounds:
1. Change the definition of the field on the form from a text field to a
time/date field.
2. Make sure the value returned by the formula is a text value by using the
@Text function in the formula for this text field.
3. Do not include a copy of the document in the message. An alternative
would be to use a doclink instead if applicable, for example, a doclink to
someone's mail file would not be appropriate.
This issue can be encountered when the included document is from users who use
the "Gray Gradient with Lines" letterhead in their mail files that are based on
the Notes 4.5x or 4.6x mail template. Take the following steps to correct this
letterhead:
1. Select Subforms in the list of design elements in the mail file or mail
template.
2. Edit the subform called "Gray Gradient and Lines." Change the field
"tmpDate" to type Time.
3. If you wish the change to the template to take effect immediately in all
mail files, run the Designer task manually from the console on the directories
when the mail files are stored. For example, if your mail files exist in a
subdirectory called MAIL, you would enter "load design \mail" at the console.
Otherwise the change will roll out to mail files that inherit from the mail
template when the Designer task runs overnight.Supporting Information:
Supporting Information:
Summary of RIP files
Summary of RIP:
-> _AllocDBlock@12+0088 <-
-> _OSAllocDBlock@12+0014 <-
-> _DPoolAlloc@16+0109 <-
-> _AllocObject@24+0049 <-
-> _OSMemAllocExtended@16+00B0 <-
-> _OSMemAlloc@12+001C <-
-> _ConvertFormulaResult@24+0082 <-
-> _TranslateFormulaResult@20+005D <-
-> _CWFEnumGuts@24+0542 <-
-> _CWFEnumGuts@24+02DE <-
-> _CWFEnum@16+0207 <-
-> _EnumCompositeBuffer@20+0047 <-
-> _NSFNoteComputeWithForm@20+00BD <-
-> _CompoundTextAddRenderedNote@16+00B6 <-
-> ?Run@CRawActionSendMail@@UAGGPAVCDefActionCtx@@PAXPAK@Z+03D1 <-
-> ?NewList@CRawAction@@MAGGPAPAVCTermList@@@Z+0026 <-
->
?RunOnAll@CAssistant@@IAGGPAVCDefActionCtx@@PAXPAPAXPAKPAUtagASSISTRUNCTXSTRUCT@
@@Z+029A <-
-> ?Run@CAssistant@@QAGGPAUtagASSISTRUNCTXSTRUCT@@@Z+0989 <-
-> _RunAssistant@20+0161 <-
-> ?Command@CAgentDocSelection@@UAGGPAUNEMSELCMD@@@Z+007B <-
-> ?ProcessCommand@CSelectionManager@@QAGHGGPAXHPAK@Z+0084 <-
-> ??0CSearchBarView@@QAE@PAVCSearchBarSubprogram@@@Z+007A <-
-> _MainWndProc@16+0848 <-
-> _CommonDlgProc@20+0014 <-
-> _DecommFindAllFiles@16+08E0 <-
The following two additional RIP summaries occurred when a customer was running
the agent as a scheduled agent:
Summary 1.
Summary of RIP:
-> _FreeDBlock@12+0038 <-
-> _OSFreeDBlockWithSize@12+006E <-
-> _OSFreeDBlock@8+001E <-
-> _Discard@4+005E <-
-> _OSMemFree@4+0046 <-
-> _OSDeletePool@4+0066 <-
-> _NSFNoteClose@4+015F <-
-> _CompoundTextAddRenderedNote@16+038B <-
-> ?Run@CRawActionSendMail@@UAGGPAVCDefActionCtx@@PAXPAK@Z+0447 <-
-> ?Run@CRawAction@@QAGGPAVCDefActionCtx@@PAXPAK@Z+0036 <-
->
?RunOnAll@CAssistant@@IAGGPAVCDefActionCtx@@PAXPAPAXPAKPAUtagASSISTRUNCTXSTRUCT@
@@Z+029B <-
-> ?Run@CAssistant@@QAGGPAUtagASSISTRUNCTXSTRUCT@@@Z+051B <-
-> _RunTask@32+04C0 <-
-> _ProcessRunMessage@4+0040 <-
-> _ProcessMessage@4+0029 <-
-> _ExecutiveMain@4+00E6 <-
-> _AddInMain@12+0115 <-
-> _NotesMain@8+0032 <-
-> _main+00F8 <-
-> _main+0017 <-
-> _mainCRTStartup+00D7 <-
Summary 2.
Summary of RIP:
-> _AllocDBlock@12+006B <-
-> _OSAllocDBlock@12+0015 <-
-> _DPoolAlloc@16+00A2 <-
-> _AllocObject@24+0047 <-
-> _OSMemAllocExtended@16+00B3 <-
-> _OSMemAlloc@12+001D <-
-> _OutputBegin@4+0017 <-
-> _ConvertItemToFormattedText@24+0015 <-
-> _AddField@8+0484 <-
-> _RenderNoteEnum@16+07DF <-
-> _EnumCompositeBuffer@20+00C5 <-
-> _CompoundTextAddRenderedNote@16+0303 <-
-> ?Run@CRawActionSendMail@@UAGGPAVCDefActionCtx@@PAXPAK@Z+0447 <-
-> ?Run@CRawAction@@QAGGPAVCDefActionCtx@@PAXPAK@Z+0036 <-
->
?RunOnAll@CAssistant@@IAGGPAVCDefActionCtx@@PAXPAPAXPAKPAUtagASSISTRUNCTXSTRUCT@
@@Z+029B <-
-> ?Run@CAssistant@@QAGGPAUtagASSISTRUNCTXSTRUCT@@@Z+051B <-
-> _RunTask@32+04C0 <-
-> _ProcessRunMessage@4+0040 <-
-> _ProcessMessage@4+0029 <-
-> _ExecutiveMain@4+00E6 <-
-> _AddInMain@12+0115 <-
-> _NotesMain@8+0032 <-
-> _main+00F8 <-
-> _main+0017 <-
-> _mainCRTStartup+00D7 <-
The following RIP summary details a crash in the SMTP MTA Outbound Message
Conversion task:
Summary 3.
Summary of RIP:
-> _AllocDBlock@12+006B <-
-> _OSAllocDBlock@12+0015 <-
-> _DPoolAlloc@16+00A2 <-
-> _AllocObject@24+0047 <-
-> _OSMemAllocExtended@16+00B3 <-
-> _OSMemAlloc@12+001D <-
-> _OSCreatePool@28+01D2 <-
-> _NSFNoteCreatePool@20+008D <-
-> _NoteOpenExtended@24+00B4 <-
-> _iNSFNoteOpenExtended@24+0080 <-
-> _NSFNoteOpenExtended@24+00A5 <-
-> _NSFNoteOpen@16+003D <-
-> _OpenCollection@20+009A <-
-> _NIFOpenCollection@40+0739 <-
-> _DesignOpenCollection@20+0075 <-
-> _DesignEnum2@32+006E <-
-> _DesignLookupNameBE@40+007E <-
-> _GetSubformNote@28+0239 <-
-> _HandleSubform@12+003F <-
-> _CWFEnum@16+05F0 <-
-> _EnumCompositeBuffer@20+00C5 <-
-> _NSFNoteComputeWithForm@20+011E <-
-> _CompoundTextAddRenderedNote@16+022D <-
-> _AddInMain@12+9DAD
-> _AddInMain@12+9BE1
-> _AddInMain@12+98A9
-> _OCNDRRecipient+11EF
-> _OCNDRRecipient+05B5
-> _OCNDRRecipient+0676
-> _AddInMain@12+632B
-> _AddInMain@12+5943
-> _AddInMain@12+09BB
-> _AddInMain@12+05A0
-> _AddInMain@12+003B
-> _AddInMain@12+0082
-> _AddInMain@12+0188
-> _AddInMain@12+00A7
-> _jinit_marker_writer+9437
The following RIP summary details a crash in the NPOP3.EXE task.
Summary 4.
Summary of RIP:
-> _OSFreeBBlock@12+001C <-
-> _OSLocalFree@4+0044 <-
-> _CHeapFree@8+0010 <-
-> _cLocalFree@8+0024 <-
-> _FreeZone@8+003D <-
-> _ComputeStop@4+010F <-
-> _NSFComputeStop@4+000C <-
-> _RunAFormula@16+0088 <-
-> _CreateItemWithFormula@24+0026 <-
-> _CWFEnumGuts@24+04FA <-
-> _CWFEnum@16+0267 <-
-> _EnumCompositeBuffer@20+00B7 <-
-> _NSFNoteComputeWithForm@20+011D <-
-> _CompoundTextAddRenderedNote@16+0146 <-
-> _OCRenderNoteToCompoundText+009A <-
-> _OCNoteToCompoundText+016E <-
-> _OCCreateMsgRendering+007B <-
-> _OCCreateBodyPartList+0032 <-
-> _OCCreateRender+001E <-
-> _OCConvertBody+0015 <-
-> _OCConvertMsg+021C <-
-> _CMConvert@16+014B <-
-> ?Export@CIMsgExport@@QAGGPAXAAVCStream@@GPAUCONVERSION_CONTROLS@@@Z+0171 <-
-> ?Export@CMessage@@IAGGPAVCStream@@@Z+0123 <-
-> ?Load@CMessage@@QAGGUtagVBLOCK@@@Z+00C9 <-
-> ?CommandLIST@CPOP3Protocol@@IAGXXZ+015F <-
-> ?StateTransaction@CPOP3Protocol@@IAGXXZ+0063 <-
-> ?Run@CPOP3Protocol@@QAGGAAUSESSIONID@@PAX@Z+0374 <-
-> ?ServerTask@@YGXH@Z+037D <-
-> _ServerThread@4+0007 <-
-> _AddInIdleDelay@4+00A4 <-
-> _AddInMain@12+01D6 <-
-> _NotesMain@8+002F <-
-> _main+00F6 <-
-> _main+0016 <-
-> _mainCRTStartup+00E3 <-
-> _TCPEndp_CheckSocketReady@12+0318 <-
-> _cmd_poll@16+01CC <-
-> _nti_poll@12+0106 <-
-> _PortDriver_AcceptWait@8+0089 <-
-> _PortDriver_WaitHelper@12+00D0 <-
-> _PortDriver_WaitExtended@12+004F <-
-> _PortDriver_Wait@12+001B <-
-> _NetWaitGuts@4+0049 <-
-> _NetWait@4+0014 <-
-> _NetQueueIOWait@8+0029 <-
-> ?Listen@CServerSession@@QAGGAAUSESSIONID@@@Z+00C1 <-
-> ?ListenerTask@@YGXH@Z+01A4 <-
-> _ListenerThread@4+0007 <-
-> _OSWaitEvent@8+001B <-
-> ?ServerTask@@YGXH@Z+00CA <-
-> _ServerThread@4+0007 <-
The following RIP summaries resulted from crashes of the HTTP task:
Summary 5.
Summary of RIP:
-> _AllocDBlock@12+0088 <-
-> _OSAllocDBlock@12+0014 <-
-> _DPoolAlloc@16+0109 <-
-> _AllocObject@24+0049 <-
-> _OSMemAllocExtended@16+00B0 <-
-> _OSMemAlloc@12+001C <-
-> ?UpdateRunData@CAssistant@@IAGGPAX00KHHPAUtagASSISTRUNCTXSTRUCT@@@Z+0135 <-
-> ?Run@CAssistant@@QAGGPAUtagASSISTRUNCTXSTRUCT@@@Z+0C4D <-
-> _AgentRun@16+0254 <-
-> ?Run@NAgent@@QAEHXZ+00C1 <-
-> ?HandleOpenAgentCmd@CmdHandler@@EAEHPAVOpenAgentCmd@@@Z+01C4 <-
-> ?PrivHandle@CmdHandlerBase@@IAEHPAVCmd@@0@Z+0136 <-
-> ?PrivHandle@CmdHandler@@EAEHPAVCmd@@@Z+007A <-
-> ?Handler@CmdHandler@@SA?AW4RequestStatus@@PAVCmd@@PAX@Z+00D6 <-
-> ?Execute@Cmd@@QAE?AW4RequestStatus@@XZ+003A <-
-> _InotesHTTPProcessRequest+026C <-
-> _InotesProcessReq+0054 <-
-> _HTAA_checkAuthorization+00FF <-
-> _RedirectionOntheFly+001C <-
-> _HTHandle+0502 <-
-> _HTSession+0590 <-
-> _HotThread+00B4 <-
Summary 6.
Summary of RIP:
-> _AllocDBlock@12+006B <-
-> _OSAllocDBlock@12+0015 <-
-> _DPoolAlloc@16+00A2 <-
-> _AllocObject@24+0047 <-
-> _OSMemAllocExtended@16+00B3 <-
-> _OSMemAlloc@12+001D <-
-> _ReadEntries@48+09C5 <-
-> _NIFReadEntries@48+0101 <-
-> _DesignEnum2@32+0109 <-
-> _DesignLookupNameBE@40+007E <-
-> _GetSharedFieldRecords@36+004E <-
-> _CWFEnum@16+017D <-
-> _EnumCompositeBuffer@20+00C5 <-
-> _NSFNoteComputeWithForm@20+011E <-
-> ?ANNValidate@ANNote@@QAEFFF@Z+009A <-
-> ?ANNValidate@ANNote@@QAEXPAULSADTMSGMETHOD@@@Z+0018 <-
-> ?ANDispatchMethod@ANNote@@UAEFPAULSADTMSGMETHOD@@@Z+014F <-
-> _ANCLASSCONTROL@16+0609 <-
->
?ClassControl@_tag_NotesADTControl@@UAGFPAULSsApiInstance@@W4LSIADTMSG@@PAULSADT
INSTDESC@@PAX@Z+001C <-
->
?AdtCallBack@LSsInstance@@QAGFP6GFPAU1@W4LSIADTMSG@@PAULSADTINSTDESC@@PAX@Z123W4
tagLSREGNAMETYPE@@@Z+0158 <-0:48:10
-> ?ProdMethodCall@LScObjCli@@QAGFKABU_GUID@@GPAULSsValue@@@Z+003F <-
-> ?AdtDoProdCallout@LSsThread@@AAGXPAULSsValue@@GPAULSsExtCallout@@@Z+008E <-
-> ?AdtCallMethod@LSsThread@@AAGXPAULSsSymbol@@@Z+0036 <-
-> ?NRun@LSsThread@@QAGFXZ+16F2 <-
-> ?Run@LSsThread@@QAGFXZ+00A4 <-
-> ?ExecuteProc@LSsThread@@QAGFPAULSsModule@@GGPAULSsValue@@G@Z+0134 <-
-> ?Run@LSsInstance@@UAGFPAULSsModule@@GGPAULSsValue@@G@Z+0272 <-
-> ?Run@LSIThread@@UAGFGH@Z+0059 <-
-> ?RunToCompletion@LSIThread@@QAGGGH@Z+0057 <-
-> ?RunScript@CLSIDocument@@UAGGPAXFPADFGPAUexecsecctx@@@Z+0206 <-
-> ?Run@CRawActionLotusScript@@UAGGPAVCDefActionCtx@@PAXPAK@Z+0240 <-
-> ?Run@CRawAction@@QAGGPAVCDefActionCtx@@PAXPAK@Z+0036 <-
-> ?Execute@CRawAction@@QAGGPAVCDefActionCtx@@@Z+00E1 <-
-> ?RunAlone@CAssistant@@IAGGPAVCDefActionCtx@@@Z+0017 <-
-> ?Run@CAssistant@@QAGGPAUtagASSISTRUNCTXSTRUCT@@@Z+05C3 <-
-> _AgentRun@16+022A <-
-> ?Run@NAgent@@QAEHXZ+007A <-
-> ?HandleSaveAgent@NDocNote@@QAEHAAV?$BasicSafePtr@E@@AAH@Z+025F <-
-> ?SaveDoc@NDocNote@@QAEHAAV?$BasicSafePtr@E@@AAH@Z+014E <-
-> ?HandleCreateDocumentCmd@CmdHandler@@AAEHPAVCreateDocumentCmd@@@Z+0212 <-
-> ?PrivHandle@CmdHandler@@AAEHPAVCmd@@@Z+01A3 <-
-> ?Handler@CmdHandler@@SA?AW4CmdStatus@Cmd@@PAV3@PAX@Z+012C <-
-> ?Execute@Cmd@@QAE?AW4CmdStatus@1@XZ+0067 <-
-> ?InotesHTTPprocessRequest@HTTP@@CAHPAU_InotesHTTPrequest@@@Z+02CE <-
-> _InotesProcessReq+00E9 <-
-> _HTHandle+057D <-
-> _HTSession+0828 <-
-> _InitializeThreads+025A <-
Summary 7.
Summary of RIP:
-> _AllocDBlock@12+006B <-
-> _OSAllocDBlock@12+0015 <-
-> _DPoolAlloc@16+00A2 <-
-> _ReallocObject@20+00C4 <-
-> _OSMemRealloc@8+0065 <-
-> _OSExtendPool@8+0067 <-
-> _AllocBlock@12+0133 <-
-> _OSAllocBlock@12+0018 <-
-> _NoteMemAlloc@16+005D <-
-> _ItemAppendByBLOCKID@32+004A <-
-> _NSFItemAppendByBLOCKID@32+003C <-
-> _NSFItemAppend@28+007A <-
-> _CreateItemWithFormula@24+0109 <-
-> _CWFEnum@16+0259 <-
-> _EnumCompositeBuffer@20+00C5 <-
-> _NSFNoteComputeWithForm@20+011E <-
-> ?ANNValidate@ANNote@@QAEFFF@Z+009A <-
-> ?ANNValidate@ANNote@@QAEXPAULSADTMSGMETHOD@@@Z+0018 <-
-> ?ANDispatchMethod@ANNote@@UAEFPAULSADTMSGMETHOD@@@Z+014F <-
-> _ANCLASSCONTROL@16+060C <-
->
?ClassControl@_tag_NotesADTControl@@UAGFPAULSsApiInstance@@W4LSIADTMSG@@PAULSADT
INSTDESC@@PAX@Z+001C <-
->
?AdtCallBack@LSsInstance@@QAGFP6GFPAU1@W4LSIADTMSG@@PAULSADTINSTDESC@@PAX@Z123W4
tagLSREGNAMETYPE@@@Z+0158 <-
-> ?ProdMethodCall@LScObjCli@@QAGFKABU_GUID@@GPAULSsValue@@@Z+003F <-
-> ?AdtDoProdCallout@LSsThread@@AAGXPAULSsValue@@GPAULSsExtCallout@@@Z+008E <-
-> ?AdtCallMethod@LSsThread@@AAGXPAULSsSymbol@@@Z+0036 <-
-> ?NRun@LSsThread@@QAGFXZ+16F2 <-
-> ?Run@LSsThread@@QAGFXZ+00A4 <-
-> ?ExecuteProc@LSsThread@@QAGFPAULSsModule@@GGPAULSsValue@@G@Z+0134 <-
-> ?Run@LSsInstance@@UAGFPAULSsModule@@GGPAULSsValue@@G@Z+0272 <-
-> ?Run@LSIThread@@UAGFGH@Z+0059 <-
-> ?RunToCompletion@LSIThread@@QAGGGH@Z+0057 <-
-> ?RunScript@CLSIDocument@@UAGGPAXFPADFGPAUexecsecctx@@@Z+0206 <-
-> ?Run@CRawActionLotusScript@@UAGGPAVCDefActionCtx@@PAXPAK@Z+0240 <-
-> ?Run@CRawAction@@QAGGPAVCDefActionCtx@@PAXPAK@Z+0036 <-
-> ?Execute@CRawAction@@QAGGPAVCDefActionCtx@@@Z+00E1 <-
-> ?RunAlone@CAssistant@@IAGGPAVCDefActionCtx@@@Z+0017 <-
-> ?Run@CAssistant@@QAGGPAUtagASSISTRUNCTXSTRUCT@@@Z+05C4 <-
-> _AgentRun@16+023F <-
-> ?Run@NAgent@@QAEHXZ+007A <-
-> ?HandleSaveAgent@NDocNote@@QAEHAAV?$BasicSafePtr@E@@AAH@Z+025F <-
-> ?SaveDoc@NDocNote@@QAEHAAV?$BasicSafePtr@E@@AAH@Z+014E <-
-> ?HandleCreateDocumentCmd@CmdHandler@@AAEHPAVCreateDocumentCmd@@@Z+0212 <-
-> ?PrivHandle@CmdHandler@@AAEHPAVCmd@@@Z+01A3 <-
-> ?Handler@CmdHandler@@SA?AW4CmdStatus@Cmd@@PAV3@PAX@Z+012C <-
-> ?Execute@Cmd@@QAE?AW4CmdStatus@1@XZ+0067 <-
-> ?InotesHTTPprocessRequest@HTTP@@CAHPAU_InotesHTTPrequest@@@Z+02CE <-
-> _InotesProcessReq+00E9 <-
-> _HTHandle+058A <-
-> _HTSession+083C <-
-> _InitializeThreads+025A <-
For more information regarding Lotus's policies and practices regarding the
Year 2000, please visit Lotus' Year 2000 web site at:
http://www.lotus.com/year2000.
This information is current as of the date set forth above, is provided for
informational purposes only, and is furnished "as is" without warranty of any
kind, express or implied. This information is not, and should not be construed
to be, a warranty or an extension or modification to the terms of any
applicable warranty. The limited warranty for Lotus products is solely as
contained in the software agreement governing your use of Lotus software.
Lotus' assessment of the Year 2000 readiness of its products is an ongoing
effort, and the information contained herein is subject to change. To ensure
you have current and accurate information about the Year 2000 readiness of
Lotus products, you should periodically refer to the Lotus Year 2000 web site.
Lotus products identified as Year 2000 ready may require user intervention,
such as the application of a maintenance release or update, or the installation
of the latest version release. The IBM Year 2000 Product Readiness Database
(accessible through Lotus' Year 2000 web site or directly at
http://www.ibm.com/year2000) includes information for Lotus software products
to denote situations in which such action may be required and includes
additional information that might prove useful to our customers and partners.
This information, other Year 2000 related Technotes published by Lotus, and all
other information contained on Lotus' and IBM's past and present Year 2000 web
site pages regarding products and services offered by Lotus, IBM and IBM's
subsidiaries are "Year 2000 Readiness Disclosures" under the Year 2000
Information and Readiness Disclosure Act of 1998, a U.S statute enacted on
October 19, 1998. This designation also applies to information delivered
through or derived from Lotus' and IBM's past and present Year 2000 web site
pages, such as electronic and printed Product Readiness Reports, various
editions of the Lotus White Papers and FAQs, and other materials.
Lotus' and IBM's Year 2000 web site pages have been and will continue to be
Lotus' primary mechanism for communicating Year 2000 information.
Copyright 2000. Lotus Development Corporation. All rights reserved.
Related Documents:
Q1 & Q2 Domino/Notes Maintenance Release Plan
Document #: 178100 More >
Last Modified on 11/16/2000
Go back
|